User installed applications in a physiological parameter display device

ABSTRACT

A physiological parameter display device displays data representing the current values of one or more physiological parameters of a patient. The device has an operating system that does not allow multiple-program execution. A program runs on the operating system. The program provides functionality that gives a user of the device an ability to install virtual applications on the device. In addition, the program provides functionality that gives the user an ability to run the virtual applications on the device while the device continues to display data representing the current value of the physiological parameter of the patient.

BACKGROUND

Physiological parameter display devices are used in a variety ofclinical settings to help caregivers learn various physiologicalparameters of patients. For example, a physiological parameter displaydevice can be used in an operating room to monitor a patient's pulserate, blood oxygen saturation level, body temperature, and bloodpressure. In another example, a physiological parameter display devicescan be used to spot check physiological parameters of patients.

In many cases, physiological parameter display devices use embeddedoperating systems to receive, process, and display data representing thecurrent values of such physiological parameters. Such embedded operatingsystems typically do not permit more than one program to execute on thephysiological parameter display devices concurrently. In other words,such embedded operating systems do not allow multiple-program execution.As a result, the functionality of the physiological parameter displaydevices is constrained while the physiological parameter display devicesare displaying data representing current values of physiologicalparameters of patients.

SUMMARY

A physiological parameter display device displays data representing thecurrent values of one or more physiological parameters of a patient. Thephysiological parameter display device has an operating system that onlyallows a single program to operate at a given time. In addition, theprogram provides functionality that gives a user of the physiologicalparameter display device an ability to add new applications to thephysiological parameter display device and/or run the new applicationson the physiological parameter display device while the physiologicalparameter display device continues to display data representing currentvalues of the one or more physiological parameters of the patient.

This summary is provided to introduce a selection of concepts. Theseconcepts are further described below in the Detailed Description. Thissummary is not intended to identify key features or essential featuresof the claimed subject matter, nor is this summary intended as an aid indetermining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example system.

FIG. 2 is a block diagram illustrating example details of a monitoringdevice.

FIG. 3 is a block diagram illustrating example details of a server.

FIG. 4 is a flowchart illustrating an example operation to install anapp on the monitoring device.

FIG. 5 is a flowchart illustrating an example operation to run an app.

FIG. 6 is a screen illustration of an example app selection interface.

FIG. 7 is a screen illustration of an example user interface of a firstapp running on the monitoring device.

FIG. 8 is a screen illustration of an example user interface of a secondapp running on the monitoring device.

FIG. 9 is a flowchart illustrating an example operation to develop anapp.

FIG. 10 is a block diagram illustrating an example computing device.

DETAILED DESCRIPTION

FIG. 1 is block diagram illustrating an example system 100. Asillustrated in the example of FIG. 1, the system 100 comprises a patient102, a monitoring device 104, a server 106, a network 108, and a user110. It should be appreciated that in other embodiments, the system 100can comprise additional people, devices, networks, and other components.For example, a different embodiment of the system 100 can comprisemultiple monitoring devices and patients in communication via thenetwork 108 with the server 106. Furthermore, the detailed descriptionand the figures describe a monitoring device. The detailed descriptionand figures can also be applicable to other classes of physiologicalparameter display devices, such as spot check devices.

The monitoring device 104 is a device that receives, on a continuingbasis, signals indicative of current values of one or more physiologicalparameters of the patient 102. In various embodiments, the monitoringdevice 104 receives signals indicative of current values of varioustypes of physiological parameters of the patient 102. For example, thephysiological parameters can include a pulse rate of the patient 102, ablood pressure of the patient 102, a blood oxygen saturation level ofthe patient 102, a body temperature of the patient 102, a respirationrate of the patient 102, a neurological activity level of the patient102, and other types of physiological parameters of the patient 102.

The monitoring device 104 can receive the signals from various types ofsensors that are in wired or wireless communication with the monitoringdevice 104. For example, the monitoring device 104 can receive thesignals from blood pressure cuffs, finger clips, thermometers,electrodes, and other types of sensors.

A program running on the monitoring device 104 processes the signalsindicative of the current values of one or more physiological parametersand causes the monitoring device 104 to display data representative ofcurrent values of the physiological parameters. The user 110 monitorsthe physiological parameters of the patient 102 by reading the currentvalues of the physiological parameters displayed by the monitoringdevice 104. For example, the program can process a signal indicative ofthe pulse rate of the patient 102 and can cause the monitoring device104 to display current values of the pulse rate of the patient 102. Inthis way, the user 110 can monitor the current pulse rate of the patient102.

The monitoring device 104 has an operating system. The operating systemdoes not allow multiple-program execution. Multiple-program execution isa form of processing in which a processing unit works on multipleprograms seemingly at the same time by parceling out the processingunit's time among the different programs. Because the operating systemdoes not allow multiple-program execution, the operating system does notparcel out the processing unit's time among multiple programs.Effectively, the operating system only allows a single program to berunning on the monitoring device 104 at any time. In other words, theoperating system does not allow multiple programs to be running on themonitoring device 104 at one time.

Because the operating system only allows a single program to be runningon the monitoring device 104 at any one time, the operating system canbe less complex than an operating system that allows multiple programsto be running on the monitoring device at one time. However, because theoperating system only allows a single program to be running on themonitoring device 104, the monitoring device 104 cannot run the programthat causes the monitoring device 104 to display data representingcurrent physiological parameters for the patient 102 while also runninganother program that provides some other functionality to the user 110.For example, the monitoring device 104 cannot run the program thatcauses the monitoring device to display parameters of the patient 102while also running a separate program that provides a Body Mass Index(BMI) calculator.

As described in detail elsewhere in the document, a single program runson the operating system. The program gives the user 110 an ability toinstall virtual applications on the monitoring device 104. In addition,the program gives the user 110 an ability to run the virtualapplications on the monitoring device 104 while the monitoring device104 continues to display data represent the current values of one ormore physiological parameters of the patient 102. Because the programprovides these abilities to the user 110, it can appear to the user 110that the user 110 is able to add new applications to the monitoringdevice 104 and run these new applications on the monitoring device 104while the monitoring device 104 continues to display data representingcurrent values of one or more physiological parameters of the patient102. The virtual applications include discrete sets of functionalityprovided by the monitoring device 104 to the user 110. The virtualapplications are virtual in the sense that they are not separateprograms operating on the monitoring device 104. For ease ofexplanation, such virtual applications are alternately referred toherein as “apps.”

FIG. 2 is a block diagram illustrating example details of the monitoringdevice 104. In various embodiments, the monitoring device 104 can be avariety of different types of devices. For example, the monitoringdevice 104 can be a portable monitoring device, such as the Connex VSM®monitor manufactured by Welch Allyn, Inc. of Skaneateles, N.Y. Inanother example, the monitoring device 104 can be a wall mountedmonitoring device. In yet another example, the monitoring device 104 canbe a handheld monitoring device. In yet another example, the monitoringdevice 104 is an electrocardiograph, such as the CP 50™electrocardiograph manufactured by Welch Allyn, Inc. of Skaneateles,N.Y.

As illustrated in the example of FIG. 2, the monitoring device 104provides a program 200, an operating system 202, a communicationinterface 204, a storage system 206, a display unit 208, and a sensorinterface 210. The communication interface 204 enables the monitoringdevice 104 to communicate with other devices via a network. The storagesystem 206 is a system of one or more computer-readable storage mediathat store data. The display unit 208 is a device for displayinginformation. The sensor interface 210 receives signals indicative ofcurrent values of physiological parameters from sensors.

The operating system 202 includes software that controls the allocationand usage of hardware resources of the monitoring device 104. Suchhardware resources can include a central processing unit, memory, datastorage devices, peripheral devices, and so on. The operating 202 onlyallows a single program to be running on the monitoring device 104 atone time. However, the operating system 202 allows multiple threads tobe running within a program at one time. In some embodiments, it is notnecessary for context switches to occur when multiple threads areoperating concurrently.

In various embodiments, the operating system 202 can be various types ofoperating system. For instance, in some embodiments, the operatingsystem 202 is a commercially available operating system, such as theThreadX operating system manufactured by Express Logic, Inc. of SanDiego, Calif.

The program 200 runs on the operating system 202. In other words, theoperating system 202 starts the program 200 and manages how the program200 uses resources of the monitoring device 104. The program 200 hasmultiple threads. As illustrated in the example of FIG. 2, the threadsinclude an app manager 212, one or more app threads 214, a sensor agent216, a file transfer module 218, a server 220, and a container 222.

The sensor agent 216 receives signals indicative of current values ofone or more physiological parameters of the patient 102 from the sensorinterface 210. The sensor agent 216 then processes the signals to causethe display unit 208 to display data representing current values of oneor more physiological parameters of the patient 102. In addition, thesensor agent 216 can store data associated with the physiologicalparameters in the storage system 206.

The app manager 212 enables the user 110 to install apps on themonitoring device 104. In various embodiments, the app manager 212enables the user 110 to install apps on the monitoring device 104 invarious ways. For example, the app manager 212 can cause the displayunit 208 to display an app installation interface. The app installationinterface allows the user 110 to select apps to install on themonitoring device 104. In this example, the app installation interfacecomprises a list of available apps. In this example, the user 110 caninstall a given app by selecting the given app from the list ofavailable apps.

When the app installation interface is displayed, the sensor agent 216continues to process signals from the sensors and continues to cause thedisplay unit 208 to display data representing the current values of thephysiological parameters of the patient 102. However, the portion of thedisplay unit 208 allocated to displaying the data representing thecurrent values of the physiological parameters is reduced while the appinstallation interface is displayed. In this way, the user 110 cancontinue to monitor the physiological parameters of the patient 102while the app installation interface is displayed.

When the user 110 selects an app to install, the file transfer module218 communicates with the server 106 to retrieve app data associatedwith the selected app. The content of the app data differs in differentembodiments and for different apps. For example, the app data for an appcan comprise an icon, a set of parameters, and a script file. In anotherexample, the app data for an app can comprise an icon, a set ofparameters, and a set of Hypertext Markup Language (HTML) documents.After retrieving the app data for the selected app, the file transfermodule 218 stores the app data for the selected app in the storagesystem 206. In some embodiments, the app data for an app can be used bycomputing devices other than monitoring devices to provide thefunctionality of the app. For example, a personal computer could use theapp data for the app to provide the same functionality as when themonitoring device 104 uses the app data.

In addition, the app manager 212 enables the user 110 to start runningapps that are installed on the monitoring device 104. In other words,the app manager 212 enables the user 110 to start providing thefunctionalities of the apps installed on the monitoring device 104. Invarious embodiments, the app manager 212 enables the user 110 to startrunning apps that are installed on the monitoring device 104 in variousways. For example, in some embodiments, the app manager 212 causes thedisplay unit 208 to display an app selection interface. In this example,the app selection interface contains one or more controls associatedwith apps installed on the monitoring device 104. The user 110 can usethese controls to select an app to run.

When the app selection interface is displayed, the sensor agent 216continues to process signals from the sensors and continues to cause thedisplay unit 208 to display data representing the current values of thephysiological parameters of the patient 102. However, the portion of thedisplay unit 208 allocated to displaying the data representing thecurrent values of the physiological parameters is reduced while the appselection interface is displayed. In this way, the user 110 can continueto monitor the physiological parameters of the patient 102 while the appselection interface is displayed. In other embodiments, the display unit208 does not display data representing the current values of thephysiological parameters while the app selection interface is displayed.

When the user 110 selects an app to run, the app manager 212 provides anidentifier of the selected app to the container 222. The container 222is a thread that provides an environment in which the selected app runs.In various embodiments, the container 222 can be implemented in variousways. For example, the container 222 can be a web browser, such as OperaMini or Opera Mobile. In another example, the container 222 can bemultimedia platform, such as Adobe Flash.

The container 222 can run the selected app in various ways. For example,the container 222 can be a web browser and the identifier of theselected app can be a URL. In this example, the container 222 retrievesa resource, such as web page data, identified by the URL. The container222 can retrieve the resource from various locations. For example, thecontainer 222 can retrieve the resource from the server 220 operating atthe monitoring device 104. In this example, the server 220 can retrievethe resource from the storage system 206 or dynamically generate theresource using data from the storage system 206 or another server. Inanother example, the container 222 can retrieve the resource from theserver 106 via the network 108. In yet another example, the container222 can retrieve the resource from a server other than the server 106via the network 108.

When the container 222 receives the resource, the container 222processes the resource. The container 222 processes different types ofresources in different ways. For example, if the resource comprises HTMLdata, the container 222 renders the HTML data to present a web page onthe display unit 208. In another example, if the resource comprisesAdobe Flash data, the container 222 starts a Flash plug-in and providesthe Flash data to the Flash plug-in.

FIG. 3 is a block diagram illustrating example details of the server106. As illustrated in the example of FIG. 3, the server 106 provides aweb server 300 and a file transfer system 302. In addition, the server106 provides an app data repository 304. In some embodiments, the server106 provides the web server 300 and the file transfer system 302 byexecuting computer-executable instructions stored on one or morecomputer storage media. The server 106 stores the app data repository304 on one or more computer storage media.

The web server 300 delivers content to client devices in response torequests from the client devices. For instance, the web server 300 candeliver web pages to the monitoring device 104 in response to requestssent by the monitoring device 104. In some instances, the web server 300can deliver content by simply retrieving the content from one or morecomputer storage media attached to the server 106 and transmitting thecontent on the network 108. However, in other instances, the web server300 can deliver content by dynamically generating the content andtransmitting the content on the network 108. In various circumstancesand embodiments, the web server 300 can dynamically generate content invarious ways. For example, in some embodiments, the web server 300 caninteract with one or more external systems to dynamically generatecontent. In this example, such external systems can include a variety ofdifferent types of systems, including Hospital Information Systems,Electronic Medical Record (EMR) systems, database systems, web servicessystems, and other types of systems that provide data.

The web server 300 is able to receive and respond to requests for avariety of different resources. For example, the web server 300 canrespond to requests for web pages, Adobe Flash data, audio/videostreams, available app lists, and so on. As discussed elsewhere in thisspecification, an available app list is a set of data that lists appsthat are available to be installed on a monitoring device.

Furthermore, the web server 300 can receive requests for app data. Whenthe web server 300 receives a request for app data for a particular appfrom a monitoring device, the web server 300 instructs the file transfersystem 302 to send the app data to the monitoring device. In response,the file transfer system 302 retrieves the app data from the app datarepository 304 and transmits the app data to the monitoring device. Invarious embodiments, the file transfer system 302 transmits the app datato the monitoring device in various ways. For example, the file transfersystem 302 can transmit the app data to the monitoring device usingHTTP, secure HTTP, the File Transfer Protocol (FTP), or anotherpublicly-available communications protocol. In another example, the filetransfer system 302 can transmit the app data to the monitoring deviceusing a proprietary communications protocol, such as the Welch AllynCommunications Protocol (WACP).

FIG. 4 is a flowchart illustrating all example operation 400 to installan app on the monitoring device 104. As illustrated in the example ofFIG. 4, the operation 400 begins when the app manager 212 receives anavailable app list from the server 106 (402). The available app listcomprises data that lists apps that are available to be installed on themonitoring device 104. The available app list can contain variousdetails about the apps. For example, the available app list can containnames of apps, textual or graphical descriptions of apps, sizerequirements of apps, user comments or ratings regarding apps, and/orother types of details about the apps. After receiving the available applist, the app manager 212 stores the available app list in the storagesystem 206 (404).

Subsequently, the program 200 receives a request from the user 110 toopen an app installation interface (406). In response, the app manager212 causes the display unit 208 to display the app installationinterface (408). The app installation interface contains informationregarding at least some of the apps listed in the available app list. Insome embodiments, the app manager 212 can provide search tools thatallow the user 110 to provide search criteria to the app manager 212. Inthis example, the app installation interface lists available apps thatare responsive to the search criteria provided by the user 110. When theapp installation interface is displayed, the monitoring device 104continues to display current data representing the current values of thephysiological parameters of the patient 102.

Next, the app manager 212 receives app installation input from the user110 via the app installation interface (410). The app installation inputis a request by the user 110 to install an app on the monitoring device104. The app manager 212 receives the app installation input when theuser 110 selects the app from the list of available apps displayed inthe app installation interface.

In response to receiving the app installation input from the user 110,the app manager 212 sends a request to the server 106 for app data forthe selected app (412). Subsequently, the app manager 212 receives theapp data for the selected app (414). After receiving the app data forthe selected app, the app manager 212 stores the app files for theselected app in the storage system 206 (416). In some embodiments, theuser 110 may need to agree to a license before receiving the app data orbefore running the selected app. The license may be from a developer ofthe selected app and/or from a distributor of the selected app (i.e., anentity operating the server 106).

FIG. 5 is a flowchart illustrating an example operation 500 to run anapp. As illustrated in the example of FIG. 5, the operation 500 beginswhen the program 200 receives a request from the user 110 to display anapp selection interface (502). In response to the request to display theapp selection interface, the app manager 212 causes the display unit 208to display the app selection interface (504). The app selectioninterface comprises controls associated with apps installed on themonitoring device 104. In various embodiments, the controls in the appselection interface can have various forms. For example, the controls inthe app selection interface can comprise selectable icons. In thisexample, the downloaded app data for the installed apps include theicons. The app manager 212 retrieves the icons from the storage system206 when the app manager 212 generates the app selection interface. Inanother example, the controls in the app selection interface cancomprise selectable icons with textual titles. In yet another example,the controls in the app selection interface can comprise textualdescriptions of installed apps with associated radio button controls.

FIG. 6 is a screen illustration of an example app selection interface600. The app selection interface 600 is a user interface displayed bythe display unit 208 of the monitoring device 104. As illustrated in theexample of FIG. 6, the app selection interface 600 comprises a parameterpane 602. The parameter pane 602 contains data representing currentvalues of physiological parameters of the patient 102. In the example ofFIG. 6, the parameter pane 602 includes data representing the currentvalues of the systolic and diastolic blood pressures of the patient 102,the blood oxygen saturation of the patient 102, the pulse rate of thepatient 102, and the body temperature of the patient 102.

In addition to the parameter pane 602, the app selection interface 600comprises an app selection pane 604. The app selection pane 604 containsicons 606 associated with apps installed on the monitoring device 104.The app selection pane 604 also includes a scroll bar 608. When the appselection pane 604 does not have enough space to show the iconsassociated with all of the apps installed on the monitoring device 104,the user 110 can use the scroll bar 608 to cause the app selection pane604 to reveal icons associated with additional apps. In the example ofFIG. 6, the user 110 can provide app selection input to the app manager212 by touching one of the icons 606.

Reference is now made again to FIG. 5. When the app selection interfaceis displayed, the app manager 212 receives an app selection input fromthe user 110 via the app selection interface (506). The app selectioninput indicates one of the installed apps. In various embodiments, theapp manager 212 receives the app selection input in various ways. Forexample, in embodiments where the app selection interface comprisesselectable icons associated with installed apps, the app manager 212 canreceive the app selection input when the user 110 selects one of theicons. In another example, in embodiments where the app selectioninterface comprises radio button controls associated with installedapps, the app manager 212 receives the app selection input when the user110 selects one of the radio button controls and then selects a submitbutton.

In response to receiving the app selection input, the app manager 212provides an identifier of the selected app to the container 222 (508).In various embodiments, the app manager 212 provides the identifier ofthe selected app to the container 222 in various ways. For example, insome embodiments, the container 222 can be a web browser and theidentifier of the selected app can be a URL. In this example, the appmanager 212 provides the URL to the web browser.

After the app manager 212 provides the identifier of the selected app tothe container 222, the container 222 runs the selected app (510). Whenthe container 222 runs the selected app, the container 222 causes thedisplay unit 208 to display an app interface. The app interface containstext, images, video, or other information belonging to one or more apps.In some embodiments in which the container 222 is a web browser, the appinterface does not include conventional web navigation controls, such asa back button, a forward button, a home button, a reload button, anaddress bar, and so on. Consequently, it may appear to the user that themonitoring device 104 is running the selected app natively. Because theuser 110 is not provided with any indication that the selected app isrunning through a web browser, it may appear to the user 110 like theselected app is actually running as a separate application on themonitoring device 104.

Furthermore, when the app interface is displayed, the monitoring device104 continues to display current data representing the physiologicalparameters of the patient 102. The monitoring device 104 is able tocontinue displaying current parameter data of the patient 102 becausethe sensor agent 216 and the container 222 execute as separate threads.In other embodiments, the display unit 208 does not display datarepresenting the current values of the physiological parameters whilethe app interface is displayed.

The container 222 runs various types of apps in various ways. Forexample, the container 222 can be a web browser and the selected app cancomprise a set of web pages. In this example, the container 222 runs theselected app by requesting the HTML documents from a server, such as theserver 220 or the web server 300. In this example, the HTML documentscan be static or dynamically-generated web pages. Upon receiving theHTML documents, the container 222 renders the HTML documents in the appinterface. Furthermore, in this example, the HTML documents can containembedded scripts, such as JavaScript scripts or VBScript scripts. Thecontainer 222 can process these embedded scripts as part of renderingthe web pages and/or after the container 222 renders such web pages.

In another example, the container 222 runs the selected app byrequesting Extensible Markup Language (XML) documents from a server,such as the server 220 or the web server 300. The container 222processes the XML documents to cause the app interface to containvarious elements.

In yet another example, the container 222 is a Flash player. In thisexample, the container 222 runs the selected app by retrieving a Flashfile from a server, such as the server 220 or the web server 300. Thecontainer 222 then processes the Flash file to display various elementsin the app interface.

In yet another example, the container 222 is a script interpreter. Inthis example, the container 222 runs the selected app by requesting oneor more scripts from a server, such as the server 220 or the web server300, or by requesting one or more scripts from the storage system 206.Upon receiving the one or more scripts, the container 222 interprets thescripts and performs the commands indicated by the scripts. As partperforming the commands indicated by the scripts, the container 222 caninitialize and start one or more of the app threads 214. The app threads214 operate within the program 200. The app threads 214 can providevarious functionalities. For example, one of the app threads 214 canprocess a physiological parameter of the patient and update a chart onan ongoing basis.

In yet another example, the container 222 is an execution environmentfor binary executable files. For instance, the app data can includecompiled Java file and the container 222 can be a Java Virtual Machine.In another instance, the app data can include one or more compiled .NETassemblies and the container 222 can be a Common Language Runtime.

FIG. 7 is a screen illustration of an example user interface 700 of afirst app running on the monitoring device 104. The user interface 700is a user interface displayed by the display unit 208 of the monitoringdevice 104. In some embodiments, the monitoring device 104 displays theuser interface 700 when the user 110 selects one of the icons 606 fromthe app selection interface 600.

As illustrated in the example of FIG. 7, the user interface 700comprises a parameter pane 702. The parameter pane 702 contains datarepresenting current values of physiological parameters of the patient102. In the example of FIG. 7, the parameter pane 702 includes datarepresenting the current values of systolic and diastolic bloodpressures of the patient 102, the blood oxygen saturation of the patient102, the pulse rate of the patient 102, and the body temperature of thepatient 102.

In addition to the parameter pane 702, the user interface 700 containsan app pane 704. The app pane 704 contains user interface elements thatare specific to an app. The app pane 704 contains a weight control 706and a height control 708. The weight control 706 and the height control708 allow the user 110 to enter a weight and a height. The app pane 704also includes numeric keypad controls 710 that allow the user 110 toenter numbers into the weight control 706 and the height control 708.The app pane 704 also includes a calculate control 712. When the user110 has entered numbers into the weight control 706 and the heightcontrol 708 and the user 110 selects the calculate control 712, a bodymass index (BMI) is displayed in a BMI control 714 in the app pane 704.

FIG. 8 is a screen illustration of a user interface 800 of a second apprunning on the monitoring device 104. The user interface 800 is a userinterface displayed by the display unit 208 of the monitoring device104. In some embodiments, the monitoring device 104 displays the userinterface 800 when the user 110 selects one of the icons 606 from theapp selection interface 600.

As illustrated in the example of FIG. 8, the user interface 800comprises a parameter pane 802. The parameter pane 802 contains datarepresenting current values of physiological parameters of the patient102. In the example of FIG. 8, the parameter pane 802 contains datarepresenting current the current values of systolic and diastolic bloodpressures of the patient 102, the blood oxygen saturation of the patient102, the pulse rate of the patient 102, and the body temperature of thepatient 102.

In addition to the parameter pane 802, the user interface 800 containsan app pane 804. The app pane 804 contains user interface elements thatare specific to an app. The app pane 804 comprises a pulse rate chart806 and a blood oxygen saturation chart 808. The pulse rate chart 806shows readings of the pulse rate of the patient 102 over time. The bloodoxygen saturation chart 808 shows readings of the blood oxygensaturation of the patient 102 over time. The second app can dynamicallygenerate the pulse rate chart 806 and the blood oxygen saturation chart808 using data generated by sensors attached to the monitoring device104, data retrieved from the server 220, data retrieved from the webserver 300, and/or using data retrieved from another source.

FIG. 9 is a flowchart illustrating an example operation 900 to developan app that can run on the monitoring device 104. As illustrated in theexample of FIG. 9, a developer can first develop the app in adevelopment environment (902). The development environment is a set ofone or more computers used by the developer to develop apps. Monitoringdevices used by the end users cannot retrieve app data from thedevelopment environment.

After initially developing the app, the developer runs the app using thedevelopment environment (904). Running the app using the developmentenvironment provides the developer with an opportunity to determinewhether the app is functioning correctly. After running the app usingthe development environment, the developer debugs the app using thedevelopment environment (906). Debugging the app can include editingsoftware code, modifying HTML or XML files, editing graphics or othermedia, and other tasks to ensure the app provides the correctfunctionality. The developer can iterate through the process of runningthe app and debugging the app in the development environment multipletimes.

When the developer is satisfied with the functionality and appearance ofthe app, the developer submits the app for approval by an appdistributor (908). The app distributor is an entity that is responsiblefor controlling which apps are available to be installed on monitoringdevices. In various embodiments, the app distributor can be varioustypes of entities. For example, the app distributor can be an enterprisethat manufactures monitoring devices. In another example, the appdistributor can be an entity that operates the server 106.

Upon receiving the app from the developer, the app distributor conductsan approval process to determine whether the app should be allowed to beinstalled on monitoring devices. If the app distributor approves theapp, the app becomes available for installation on monitoring devices,such as the monitoring device 104. If the app distributor rejects theapp, the app distributor notifies the developer and can inform thedeveloper why the app distributor did not approve the app. The appdistributor can reject the app for a variety of reasons. For example,the app distributor can reject the app if the app does not functionproperly, poses a security risk, contains inappropriate content, or ifthe app does not meet various other criteria.

FIG. 10 is a block diagram illustrating an example computing device1000. In some embodiments, the monitoring device 104 and/or the server106 are implemented using one or more computing devices like thecomputing device 1000. It should be appreciated that in otherembodiments, the monitoring device 104 and/or the server 106 areimplemented using computing devices having hardware components otherthan those illustrated in the example of FIG. 10.

In different embodiments, computing devices are implemented in differentways. For instance, in the example of FIG. 10, the computing device 1000comprises a memory 1002, a processing system 1004, a secondary storagedevice 1006, a network interface card 1008, a video interface 1010, adisplay unit 1012, an external component interface 1014, and acommunication medium 1016. In other embodiments, computing devices areimplemented using more or fewer hardware components. For instance, inanother example embodiment, a computing device does not include a videointerface, a display unit, an external storage device, or an inputdevice.

The term computer readable media as used herein may include computerstorage media. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Thememory 1002 includes one or more computer storage media capable ofstoring data and/or instructions. As used in this document, a computerstorage medium is a device or article of manufacture that stores dataand/or software instructions readable by a computing device. Indifferent embodiments, the memory 1002 is implemented in different ways.For instance, in various embodiments, the memory 1002 is implementedusing various types of computer storage media. Example types of computerstorage media include, but are not limited to, dynamic random accessmemory (DRAM), double data rate synchronous dynamic random access memory(DDR SDRAM), reduced latency DRAM, DDR2 SDRAM, DDR3 SDRAM, Rambus RAM,solid state memory, flash memory, read-only memory (ROM),electrically-erasable programmable ROM, and other types of devicesand/or articles of manufacture that store data.

The term computer readable media as used herein may also includecommunication media. Communication media may be embodied by computerreadable instructions, data structures, program modules, or other datain a modulated data signal, such as a carrier wave or other transportmechanism, and includes any information delivery media. The term“modulated data signal” may describe a signal that has one or morecharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia may include wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),infrared, and other wireless media.

The processing system 1004 includes one or more physical integratedcircuits that selectively execute software instructions. In variousembodiments, the processing system 1004 is implemented in various ways.For example, the processing system 1004 can be implemented as one ormore processing cores. In this example, the processing system 1004 cancomprise one or more Intel Core 2 microprocessors. In another example,the processing system 1004 can comprise one or more separatemicroprocessors. In yet another example embodiment, the processingsystem 1004 can comprise an ASIC that provides specific functionality.In yet another example, the processing system 1004 provides specificfunctionality by using an ASIC and by executing software instructions.In another example, the processing system 1004 is an ARM7 processor. Indifferent embodiments, the processing system 1004 executes softwareinstructions in different instruction sets. For example, the processingsystem 1004 executes software instructions in instruction sets such asthe x86 instruction set, the POWER instruction set, a RISC instructionset, the SPARC instruction set, the IA-64 instruction set, the MIPSinstruction set, and/or other instruction sets.

The secondary storage device 1006 includes one or more computer storagemedia. The secondary storage device 1006 stores data and softwareinstructions not directly accessible by the processing system 1004. Inother words, the processing system 1004 performs an I/O operation toretrieve data and/or software instructions from the secondary storagedevice 1006. In various embodiments, the secondary storage device 1006is implemented by various types of computer-readable data storage media.For instance, the secondary storage device 1006 may be implemented byone or more magnetic disks, magnetic tape drives, CD-ROM discs, DVD-ROMdiscs, Blu-Ray discs, solid state memory devices, Bernoulli cartridges,and/or other types of computer-readable data storage media.

The network interface card 1008 enables the computing device 1000 tosend data to and receive data from a communication network. In differentembodiments, the network interface card 1008 is implemented in differentways. For example, in various embodiments, the network interface card1008 is implemented as an Ethernet interface, a token-ring networkinterface, a fiber optic network interface, a wireless network interface(e.g., WiFi, WiMax, etc.), or another type of network interface.

The video interface 1010 enables the computing device 1000 to outputvideo information to the display unit 1012. In different embodiments,the video interface 1010 is implemented in different ways. For instance,in one example embodiment, the video interface 1010 is integrated into amotherboard of the computing device 1000. In another example embodiment,the video interface 1010 is a video expansion card. In variousembodiments, the display unit 1012 can be a cathode-ray tube display, anLCD display panel, a plasma screen display panel, a touch-sensitivedisplay panel, an LED screen, a projector, or another type of displayunit. In various embodiments, the video interface 1010 communicates withthe display unit 1012 in various ways. For example, the video interface1010 can communicate with the display unit 1012 via a Universal SerialBus (USB) connector, a VGA connector, a digital visual interface (DVI)connector, an S-Video connector, a High-Definition Multimedia Interface(HDMI) interface, a DisplayPort connector, or another type ofconnection.

The external component interface 1014 enables the computing device 1000to communicate with external devices. In various embodiments, theexternal component interface 1014 is implemented in different ways. Forexample, the external component interface 1014 can be a USB interface, aFireWire interface, a serial port interface, a parallel port interface,a PS/2 interface, and/or another type of interface that enables thecomputing device 1000 to communicate with external devices. In differentembodiments, the external component interface 1014 enables the computingdevice 1000 to communicate with different external components. Forexample, the external component interface 1014 can enable the computingdevice 1000 to communicate with external storage devices, input devices,speakers, phone charging jacks, modems, media player docks, othercomputing devices, scanners, digital cameras, a fingerprint reader, andother devices that can be connected to the computing device 1000.Example types of external storage devices include, but are not limitedto, magnetic tape drives, flash memory modules, magnetic disk drives,optical disc drives, flash memory units, zip disk drives, opticaljukeboxes, and other types of devices comprising one or more computerstorage media. Example types of input devices include, but are notlimited to, keyboards, mice, trackballs, stylus input devices, key pads,microphones, joysticks, touch-sensitive display screens, and other typesof devices that provide user input to the computing device 1000.

The communications medium 1016 facilitates communication among thehardware components of the computing device 1000. In differentembodiments, the communications medium 1016 facilitates communicationamong different components of the computing device 1000. For instance,in the example of FIG. 10, the communications medium 1016 facilitatescommunication among the memory 1002, the processing system 1004, thesecondary storage device 1006, the network interface card 1008, thevideo interface 1010, and the external component interface 1014. Indifferent implementations of the computing device 1000, thecommunications medium 1016 is implemented in different ways. Forinstance, in different implementations of the computing device 1000, thecommunications medium 1016 may be implemented as a PCT bus, a PCTExpress bus, an accelerated graphics port (AGP) bus, an Infinibandinterconnect, a serial Advanced Technology Attachment (ATA)interconnect, a parallel ATA interconnect, a Fiber Channel interconnect,a USB bus, a Small Computing system Interface (SCSI) interface, oranother type of communications medium.

The memory 1002 stores various types of data and/or softwareinstructions. For instance, in the example of FIG. 10, the memory 1002stores a Basic Input/Output System (BIOS) 1024, and an operating system1026. The BIOS 1024 includes a set of software instructions that, whenexecuted by the processing system 1004, cause the computing device 1000to boot up. The operating system 1026 includes a set of softwareinstructions that, when executed by the processing system 1004, causethe computing device 1000 to provide an operating system thatcoordinates the activities and sharing of resources of the computingdevice 1000.

The various embodiments described above are provided by way ofillustration only and should not be construed as limiting. Those skilledin the art will readily recognize various modifications and changes thatmay be made without following the example embodiments and applicationsillustrated and described herein. For example, the operations shown inthe figures are merely examples. In various embodiments, similaroperations can include more or fewer steps than those shown in thefigures. Furthermore, in other embodiments, similar operations caninclude the steps of the operations shown in the figures in differentorders.

What is claimed is:
 1. A patient monitoring device, comprising: aprocessing unit; a display unit; and memory storing instructions that,when executed by the processing unit, cause the patient monitoringdevice to: execute one operating system that only supportssingle-program execution; and execute a single program that runs on theone operating system, the single program providing functionality to:receive at least one physiological parameter signal of a patient;display a parameter pane on the display unit in an expanded view,wherein the parameter pane comprises data representing a current valueof a physiological parameter associated with the at least onephysiological parameter signal; install and execute multipleapplications on the one operating system of the patient monitoringdevice; receive a user request to display on the display unit an appselection interface while displaying the parameter pane in the expandedview; display the app selection interface in response to the userrequest, the app selection interface comprising: the parameter pane,displayed in a first portion of the display unit, contains the datarepresenting the current value of the physiological parameter of thepatient in a reduced view; an app selection pane, displayed in a secondportion of the display unit, that contains icons associated with themultiple applications installed on the patient monitoring device andcontrols that cause one of the multiple applications to run on thepatient monitoring device, each application operating within the singleprogram; and run at least one of the multiple applications in responseto selection of an app from the app selection pane and display an appinterface in the second portion of the display unit on the one operatingsystem of the patient monitoring device while the patient monitoringdevice continues to display data representing the current value of thephysiological parameter in the first portion of the display unit,wherein the applications are discrete sets of functionality provided bythe patient monitoring device to a user.
 2. The patient monitoringdevice according to claim 1, wherein the single program additionallyprovides functionality to: receive an available app list from a server,the available app list including data listing apps that are available tobe installed on the patient monitoring device; cause the display unit todisplay an app installation interface; receive app installation inputincluding a selected app, wherein the display unit continues to displaythe current value of the physiological parameter; and send a request tothe server for app data for the selected app.
 3. The patient monitoringdevice according to claim 2, wherein the single program additionallyprovides functionality to: receive the app data for the selected app,the app data including app files; store the app files in the memory; anddetermine whether the selected app requires a license agreement.
 4. Thepatient monitoring device according to claim 1, wherein the singleprogram additionally provides functionality to: receive an app selectioninput via the app selection interface, the app selection inputindicating a given application; and using a thread within the singleprogram to run the given application.
 5. The patient monitoring deviceaccording to claim 1, wherein the physiological parameter is one of thefollowing: blood pressure, blood oxygen saturation, pulse rate, and bodytemperature.
 6. The patient monitoring device according to claim 4,wherein the single program additionally provides functionality to: storeapp data for the given application in the memory; and run a containerthread within the single program, the container thread running the givenapplication by processing the app data for the given application.
 7. Thepatient monitoring device according to claim 6, wherein the containerthread comprises at least one of: a web browser, a multimedia platform,a script interpreter, and an execution environment for binary executablefiles.
 8. The patient monitoring device according to claim 7, wherein torun the given application, the container thread retrieves data from theserver.
 9. The patient monitoring device according to claim 8, whereinthe single program additionally provides functionality to: run theserver as a thread within the single program.
 10. The patient monitoringdevice according to claim 9, wherein the container thread starts thethread for the given application when the container thread processes theapp data for the given application.
 11. A method implemented on aphysiological parameter display device, the method comprising: executingone operating system that only allows a single program to be executed;and executing the single program that runs on the one operating system,the single program providing functionality to: receive at least onephysiological parameter signal of a patient; display a parameter pane ona display unit of the physiological parameter display device, whereinthe parameter pane comprises data representing a current value of aphysiological parameter associated with the at least one physiologicalparameter signal, the parameter pane being displayed in an expandedview; receive a user request to display an app selection interface whiledisplaying the parameter pane in the expanded view, display the appselection interface in response to the user request, wherein the appselection interface allows a user to select applications to install andexecute on the one operating system of the physiological parameterdisplay device, the app selection interface including the parameter paneand an app selection pane, wherein the parameter pane, displayed in afirst portion of the display unit, includes a display of the currentphysiological parameter data in a reduced view, and wherein the appselection pane, displayed in a second portion of the display unit,includes selectable icons, with each of the selectable icons havingcontrols that cause one of the applications to be run on the oneoperating system of the physiological parameter display device, eachapplication operating within the single program; run at least one of themultiple applications in response to selection of an app from the appselection pane and display an app interface in the second portion of thedisplay unit on the one operating system of the patient monitoringdevice while the patient monitoring device continues to display datarepresenting the current value of the physiological parameter in thefirst portion of the display unit, wherein the applications are discretesets of functionality provided by the patient monitoring device to auser.
 12. The method according to claim 11, wherein executing the singleprogram further provides functionality to: provide an app installationinterface; install the applications on the physiological parameterdisplay device; and run the applications on the physiological parameterdisplay device while the physiological parameter display devicecontinues to display data representing a current value of thephysiological parameter, wherein the applications are discrete sets offunctionality provided by the physiological parameter display device tothe user; and wherein each application operates within the singleprogram.
 13. The method according to claim 12, wherein executing thesingle program further provides functionality to: receive appinstallation input from the user via the app installation interface, theapp installation input being a request by the user to install a givenapplication on the physiological parameter display device; in responseto receiving the app installation input, send a request to a server forapp data for the given application; receive the app data for the givenapplication; and store the app data for the given application in astorage system at the physiological parameter display device.
 14. Themethod according to claim 12, wherein the applications include a givenapplication; wherein the method further comprises: storing app data forthe given application in a storage system at the physiological parameterdisplay device; and wherein executing the single program comprises:running a container thread within the single program, the containerthread running the given application by processing the app data for thegiven application.
 15. The method according to claim 14, wherein thecontainer thread comprises at least one of: a web browser, a multimediaplatform, a script interpreter, and an execution environment for binaryexecutable files.
 16. The method according to claim 14, wherein to runthe given application, the container thread retrieves data from aserver; and wherein executing the single program further comprisesrunning the server as a thread within the single program.
 17. The methodaccording to claim 14, wherein the container thread starts the threadfor the given application when the container thread processes the appdata for the given application.
 18. A physiological parameter displaydevice, comprising: a processing unit; a display unit; and memorystoring instructions that, when executed by the processing unit, causethe patient monitoring device to: execute one operating system thatallows only single-program execution; and execute a single program thatruns on the one operating system, the single program providingfunctionality to: receive at least one physiological parameter signal ofa patient; display a parameter pane on the display unit in an expandedview, wherein the parameter pane comprises data representing a currentvalue of a physiological parameter associated with the at least onephysiological parameter signal; install and execute multipleapplications on the one operating system of the physiological parameterdisplay device; receive a user request while displaying the parameterpane in the expanded view causing the display unit of the physiologicalparameter display device to display an app selection interface, the appselection interface including the parameter pane and an app selectionpane, wherein the parameter pane, displayed in a first portion of thedisplay unit, includes a display of current physiological parameter datain a reduce view; wherein the app selection pane, displayed in a secondportion of the display unit, includes selectable icons, with each of theselectable icons having controls that cause one of the applications tobe run on the one operating system of the physiological parameterdisplay device, each application operating within the single program;and run at least one of the multiple applications in response toselection of an app from the app selection pane and display an appinterface in the second portion of the display unit on the one operatingsystem of the physiological parameter display device while thephysiological parameter display device continues to display datarepresenting the current value of the physiological parameter in thefirst portion of the display unit, wherein the applications are discretesets of functionality provided by the patient monitoring device to auser.
 19. The patient monitoring device according to claim 1, whereinthe app selection pane includes a scroll bar allowing the user to causethe app selection pane to reveal icons associated with additional appswhen the app selection pane does not have enough space to show iconsassociated with all of the apps installed on the patient monitoringdevice.